From ad1148687cdac6d4185684c668975da9d174fc86 Mon Sep 17 00:00:00 2001 From: Tay Caliguiri Date: Thu, 19 Feb 2026 15:40:25 -0500 Subject: [PATCH 1/6] Moved KB from NAA to AIC --- ...pear_in_the_aic_or_reporting_console_after_scoping_changes.md | 1 + 1 file changed, 1 insertion(+) rename docs/kb/{accessanalyzer/reports-and-web-console => accessinformationcenter/reports}/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md (98%) diff --git a/docs/kb/accessanalyzer/reports-and-web-console/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md similarity index 98% rename from docs/kb/accessanalyzer/reports-and-web-console/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md rename to docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index 5fdda7ef27..f0e64acdb3 100644 --- a/docs/kb/accessanalyzer/reports-and-web-console/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -12,6 +12,7 @@ title: "Out-of-Scope Resources Still Appear in the AIC or Reporting Console Afte knowledge_article_id: kA0Qk0000002mDRKAY products: - access-analyzer + - access-information-center --- # Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes From b5305d32de8388abd6eff3c563120ba1f1964b12 Mon Sep 17 00:00:00 2001 From: Hil-Ram-NWX Date: Thu, 19 Feb 2026 23:51:44 -0500 Subject: [PATCH 2/6] Proofreading Edits Fix broken links and style issue: - Fix broken links to dropping_file_system_data (2 occurrences) - Change from absolute path with .md to relative path without extension - Update path: ../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data - Change "included/excluded" to "included or excluded" --- ...reporting_console_after_scoping_changes.md | 37 +++++++++++-------- 1 file changed, 21 insertions(+), 16 deletions(-) diff --git a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index f0e64acdb3..54abddea53 100644 --- a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -1,42 +1,47 @@ --- description: >- - This article explains how out-of-scope File System resources continue to appear in the Access Information Center (AIC) and reporting console after scoping changes, along with the steps to resolve this issue. + Learn why out-of-scope File System resources may continue to appear in the Access Information Center (AIC) or reporting console after scoping changes, and how to remove the retained data from the database. keywords: - File System resources - Access Information Center - - scoping changes -sidebar_label: Out-of-Scope Resources in AIC -tags: - - reports-and-web-console -title: "Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes" -knowledge_article_id: kA0Qk0000002mDRKAY + - AIC + - scoping rules + - FSAA scan + - SEEK scan + - Netwrix Access Analyzer + - drop file system data + - reporting console products: - access-analyzer - access-information-center +sidebar_label: Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes +title: Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes +knowledge_article_id: kA0Qk0000002mDRKAY --- # Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes ## Symptom -File System resources that were previously scanned and imported continue to appear in the database, even after scoping options have been updated to exclude them. These resources do not show up in new FSAA/SEEK scans but still exist in the backend database, causing them to still show in the Access Information Center (AIC) and reports. +File System resources that were previously scanned and imported continue to appear in the database, even after scoping options have been updated to exclude them. These resources do not appear in new FSAA or SEEK scans but still exist in the backend database, causing them to remain visible in the Access Information Center (AIC) and reports. ## Cause -Scoping options are applied at the time of a scan and are used to determine which resources are included/excluded in that specific FSAA/SEEK scan. If a resource was imported before the scoping rules were put in place, it remains in the database, regardless of whether it is currently in scope. +Scoping options are applied at the time of a scan and are used to determine which resources are included or excluded in that specific FSAA or SEEK scan. If a resource was imported before the scoping rules were put in place, it remains in the database, regardless of whether it is currently in scope. ## Resolution If you no longer want to retain or see data for out-of-scope resources: -1. **Delete all File System data** for the specific host from the database. - - See the following article for instructions to drop data for a specific file server: [How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data.md). +1. **Delete all File System data** for the specific host from the database. + See the following article for instructions to drop data for a specific file server: + [How to Drop File System Data from Netwrix Access Analyzer](../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) -2. **Rescan the host** with the updated scoping rules in place. - - This will ensure that only resources matching the current scoping criteria are imported and retained going forward. +2. **Rescan the host** with the updated scoping rules in place. + This ensures that only resources matching the current scoping criteria are imported and retained going forward. -> **NOTE:** While out-of-scope resources remain in the database, they will not be included in future scans or updated during bulk imports unless brought back into scope. +> **NOTE:** While out-of-scope resources remain in the database, they are not included in future scans or updated during bulk imports unless they are brought back into scope. -## Related Link +## Related Links -- [How to Drop File System Data from Netwrix Access Analyzer](/docs/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data.md) \ No newline at end of file +- [How to Drop File System Data from Netwrix Access Analyzer](../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) From 083b7c7b47aadb12f54b41aba4abfd5a27f308bd Mon Sep 17 00:00:00 2001 From: Hil-Ram-NWX Date: Fri, 20 Feb 2026 00:06:23 -0500 Subject: [PATCH 3/6] minor updates - Updated sidebar label and title formatting for clarity. - Changed 'Related Links' to 'Related Link' --- ...in_the_aic_or_reporting_console_after_scoping_changes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index 54abddea53..568a88ce03 100644 --- a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -14,8 +14,8 @@ keywords: products: - access-analyzer - access-information-center -sidebar_label: Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes -title: Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes +sidebar_label: "Out-of-Scope Resources in AIC" +title: "Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes" knowledge_article_id: kA0Qk0000002mDRKAY --- @@ -42,6 +42,6 @@ If you no longer want to retain or see data for out-of-scope resources: > **NOTE:** While out-of-scope resources remain in the database, they are not included in future scans or updated during bulk imports unless they are brought back into scope. -## Related Links +## Related Link - [How to Drop File System Data from Netwrix Access Analyzer](../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) From f23a5d4fd7a3217503fb169d681a3440efa88ed0 Mon Sep 17 00:00:00 2001 From: hilram7 Date: Fri, 20 Feb 2026 10:08:10 -0500 Subject: [PATCH 4/6] Fix broken links in AIC KB article Changed relative paths to Docusaurus absolute paths to fix build errors in versioned directories. Removed /docs/ prefix and .md extension per Docusaurus path conventions. Fixes: broken links to dropping_file_system_data from versioned docs --- ..._the_aic_or_reporting_console_after_scoping_changes.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index 568a88ce03..0f82724187 100644 --- a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -33,9 +33,9 @@ Scoping options are applied at the time of a scan and are used to determine whic If you no longer want to retain or see data for out-of-scope resources: -1. **Delete all File System data** for the specific host from the database. - See the following article for instructions to drop data for a specific file server: - [How to Drop File System Data from Netwrix Access Analyzer](../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) +1. **Delete all File System data** for the specific host from the database. + See the following article for instructions to drop data for a specific file server: + [How to Drop File System Data from Netwrix Access Analyzer](/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) 2. **Rescan the host** with the updated scoping rules in place. This ensures that only resources matching the current scoping criteria are imported and retained going forward. @@ -44,4 +44,4 @@ If you no longer want to retain or see data for out-of-scope resources: ## Related Link -- [How to Drop File System Data from Netwrix Access Analyzer](../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) +- [How to Drop File System Data from Netwrix Access Analyzer](/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) From 9821505defd0a2686a39170a3e6f934054377a28 Mon Sep 17 00:00:00 2001 From: hilram7 Date: Fri, 20 Feb 2026 11:12:14 -0500 Subject: [PATCH 5/6] Fix broken links using full documentation URLs Changed from absolute Docusaurus paths to full docs.netwrix.com URLs per KB linking standards. Uses 12_0 (underscore) in URL as per Docusaurus URL conventions. Fixes: broken cross-product KB links in versioned directories --- ...r_in_the_aic_or_reporting_console_after_scoping_changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index 0f82724187..e8b2be9728 100644 --- a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -35,7 +35,7 @@ If you no longer want to retain or see data for out-of-scope resources: 1. **Delete all File System data** for the specific host from the database. See the following article for instructions to drop data for a specific file server: - [How to Drop File System Data from Netwrix Access Analyzer](/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) + [How to Drop File System Data from Netwrix Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12_0/kb/file-system-and-sensitive-data-discovery/dropping_file_system_data) 2. **Rescan the host** with the updated scoping rules in place. This ensures that only resources matching the current scoping criteria are imported and retained going forward. @@ -44,4 +44,4 @@ If you no longer want to retain or see data for out-of-scope resources: ## Related Link -- [How to Drop File System Data from Netwrix Access Analyzer](/kb/accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data) +- [How to Drop File System Data from Netwrix Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12_0/kb/file-system-and-sensitive-data-discovery/dropping_file_system_data) From 39cd7717d422dd48f6691122cfd9f85860930ca7 Mon Sep 17 00:00:00 2001 From: Hil-Ram-NWX Date: Fri, 20 Feb 2026 12:15:00 -0500 Subject: [PATCH 6/6] minor formatting revision - changed lines 41 from 'going forward' to 'in the future' - revised bold formatting (per the Documentation Reviewer feedback) --- ...in_the_aic_or_reporting_console_after_scoping_changes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md index e8b2be9728..9e5f065449 100644 --- a/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md +++ b/docs/kb/accessinformationcenter/reports/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md @@ -33,12 +33,12 @@ Scoping options are applied at the time of a scan and are used to determine whic If you no longer want to retain or see data for out-of-scope resources: -1. **Delete all File System data** for the specific host from the database. +1. Delete all **File System data** for the specific host from the database. See the following article for instructions to drop data for a specific file server: [How to Drop File System Data from Netwrix Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12_0/kb/file-system-and-sensitive-data-discovery/dropping_file_system_data) -2. **Rescan the host** with the updated scoping rules in place. - This ensures that only resources matching the current scoping criteria are imported and retained going forward. +2. Rescan the host with the updated scoping rules in place. + This ensures that only resources matching the current scoping criteria are imported and retained in the future. > **NOTE:** While out-of-scope resources remain in the database, they are not included in future scans or updated during bulk imports unless they are brought back into scope.